home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nautilus 1994 November
/
Nautilus CD Magazine Volume 4-11 November 1994 Windows Edition.mdf
/
compware
/
drivers
/
matrox
/
readme.txt
< prev
next >
Wrap
Text File
|
1994-06-27
|
9KB
|
228 lines
README.WIN MATROX ELECTRONIC SYSTEMS June 27, 1994
The MGA WINDOWS 3.1 Display Drivers
Revision 1.42
Floppy contents:
README.WIN this file
INSTALL.EXE install program
FILES1.ZIP Windows drivers and support files
FILES2.ZIP Control Panel program and support files
Installation and usage:
Use the provided install program (do not try to install manually). The
install program asks you for a start-up mode (resolution and number of
colors) for Windows, and validates it against your board's capabilities.
Inside Windows, you can use the MGA Control Panel to change modes and
activate MGA features.
Once the software is installed, you can use the Windows SETUP program to
toggle between MGA and other display drivers. Note that through SETUP
though, you only select the number of colors; the resolution is hardcoded
to 640 X 480, and needs to be adjusted afterwards through the MGA Control
Panel.
Modifications to the Windows .INI files:
The MGA Windows Driver installation program makes some changes to
various .INI files. The changes for the default installation (1024 X 768,
8-bit) are listed below:
PROGMAN.INI
===========
[Groups]
Group6=C:\WINDOWS\MGA.GRP ; actual group number will differ
WIN.INI
=======
[windows]
load=C:\MGA\CPANEL\MGAPANEL.EXE
[fonts] ; different settings for 800 X 600 and lower
Small Fonts (8514/a res)=SMALLF.FON
Symbol 8,10,12,14,18,24 (8514/a res)=SYMBOLF.FON
MS Serif 8,10,12,14,18,24 (8514/a res)=SERIFF.FON
Courier 10,12,15 (8514/a res)=COURF.FON
MS Sans Serif 8,10,12,14,18,24 (8514/a res)=SSERIFF.FON
SYSTEM.INI
==========
[boot]
386grabber=mgavga.3gr
286grabber=mgavga.2gr
display.drv=mga8.drv
oemfonts.fon=8514oem.fon ; VGA font files used for 800 X 600 and lower
fixedfon.fon=8514fix.fon
fonts.fon=8514sys.fon
[boot.description]
displayinf=oemmga.inf
aspect=100,120,120 ; different parameters used for 800 X 600 and lower
display.drv=Matrox MGA 256 colors
[386Enh]
EMMEXCLUDE=CC00-CCFF ; if board is not at AC000 default address
display=vddmga.386
[mga.drv]
DesktopHeight=768
DesktopWidth=1024
DisplayHeight=768
DisplayWidth=1024
ModeSWITCH=OFF
dpi=120 ; different parameter used for 800 X 600 and lower
DPMS screen-saver:
This version supports VESA/VBE DPMS (Display Power Managament Signaling).
It also includes a Windows screen-saver to control the delays before
entering into energy-saving modes.
The screen-saver is installed in your Windows directory, and accessible
as any other, through the Windows Control Panel, under "Desktop".
The DPMS support is handled by the MGA Virtual Display Driver(VDD), so it
is not necessary to load the MGAVESA driver included with the MGA Utilities.
Bug history:
Here is a list of bugs fixed since version 1.32.
Battle Chess - fixed GPF occuring with all drivers
MS WinHCT - no more unsupported modes with "DispTest"
CorelDraw 3.0 - fixed "radial fountain fill" bug
PowerPoint - fixed GPF with ANIMALS and garbage with GREATEST.PPT
Renderize 1.2 - fixed system lock when scrolling
MacroMedia Action - can now start Action!
PhotoCD Access - fixed missing portions of image in Large and Poster
modes
Ctrl-Alt-Del - cursor is now visible when getting back into high res
Cursor offset - fixed cursor position offset on 2+ boards
ALT key - keyboard no longer freezes when switching in full
screen
DIR A: - system no longer freezes if no diskette in drive
Pen for Windows - now supported
Hijack - fixed bug with missing pixels when drawing
complex shapes (v1.42)
In General - "Not enough memory" problem fixed with
multiple applications loaded. This also fixes
a problem with windows for workgroups. You
should be able to connect a network drive with
the FileManager.(v1.42)
KNOWN BUGS AND LIMITATIONS
Memory exclusion (ISA, MCA and VL boards):
- If Windows refuses to boot, or the display seems to be corrupted, you may
have to exclude the address space where the MGA is mapped. For example,
if your MGA is mapped at 0xC800, add the following line in the [386Enh]
section of the SYSTEM.INI file: EMMExclude=c800-cbff
Also check in your CONFIG.SYS for memory managers (such as EMM386,
QEMM386, 386MAX). If there are any, make sure that they also exclude
the address space used by the MGA board.
Grabber and VDD:
- Straight VGA DOS graphic applications will run in full screen mode, but
not in a DOS Window.
Zoom limitations:
- Zoom x4 is not supported for the following display sizes: 640x480, NTSC,
PAL, and 800x600.
- Zoom x2 and x4 do not work well in the 1024 X 768 interlaced mode; the
display looks a bit fuzzy.
Aldus Persuasion 2.1:
- This application sometimes crashes when used with either the 8-bit QCDP
or ModeSwitch driver. Workaround: use the 8-bit 256 colors or 24-bit 16.7M
colors drivers.
AfterDark 2.0
- In the Swan lake and Aquatic Realm modules, the swans and fishes going
from right to left are not displayed properly in 24 bits, QCDP and
ModeSWITCH drivers. This is an AfterDark problem and should be fixed
in a future release of the product.
- AfterDark is not recommended with the ModeSWITCH driver, because it
inquires about screen resolution only once, when starting Windows.
Therefore, if you change the display mode, AfterDark may not properly
clear the screen.
CorelDRAW! 3.0
- When you run CorelDRAW! while using the ModeSWITCH driver, files
can't be saved with a monochrome Image Header. You can save files
with the 4K or 8K color , or no Image Header.
ModeSWITCH and QCDP drivers:
- These drivers are slower than the 8-bit 256 color driver. Video for
Windows profiler may find these drivers too slow for ideal playback.
Workaround: use the 8-bit 256 colors driver.
16-bit, 24-bit, ModeSWITCH and QCDP drivers:
- The Intermission 3.0 screen saver will cause these drivers to crash if
the module SORCERY.IMX is loaded.
Device bitmaps:
- The MGA POWER Drivers supports a feature of Windows 3.1 that allows
device bitmaps to be stored in the MGA memory instead of main memory.
Device bitmaps can increase the performance of MGA drivers if there is
ample on-board memory. However, when this feature is activated,
Windows 3.1 is not 100% reliable and could cause some applications to
crash. You can disable the device bitmaps feature by adding the
following line in the MGA.DRV section of your SYSTEM.INI file.
[MGA.DRV]
.
DevBits=OFF
- DeltaGraph 2.0 may have graph samples corrupted and will cause
a GPF when it opens in 1024x768 8-bit 256 colors.
Workaround: disable device bitmaps.
Cursor with PixelTouch:
- On the PCI/2+ and VLB/2+ boards, the cursor may be incorrect when using
PixelTouch. This problem has been seen at least with the 8-bit driver, in
1024 X 768 and 1280 X 1024 resolutions. The effect is an extra line just
underneath the cursor, when zooming by 4. Workaround: The 72 Hz monitor
file happens to have video timings which alleviate the problem. If your
monitor supports this frequency, we recommend it. This limitation will be
fixed in the next version of the drivers.
VGA applications:
MGA with a monochrome card:
- The MGA Windows drivers do not work when a monochrome card is installed
in the system and the MGA card has its VGA disabled.
- (PCI boards only) A monochrome card will not be recognized if the MGA
has its VGA enabled. The system will boot, but the monochrome card will be
unusable (i.e. "mode mono" will do nothing).
Beta Windows "Chicago":
- All included drivers except for the ModeSwitch one will work with the Beta
versions of Chicago.
Pen for Windows:
- Used with the CIC HandWriter, GPF's can occur in your application while
doing hand writing recognition. Workaround: use only the 8 bpp (256 color)
driver.